Problem Note 35391: Deny ReadMetadata and WriteMetadata causes a duplicate Shared Data folder to be created.
A duplicate Shared Data folder might be created under the BI Manager in SAS® Management Console when a new SAS library is created by a metadata identity that has been denied ReadMetadata and WriteMetadata on the existing Shared Data folder under BI Manager. Metadata identity permisions are inherited from the BIP Service which is located under:
Authorization Manager ► Resource Management ► By Application ► BIP Service
When a duplicate Shared Data folder is created, every metadata identity with ReadMetadata and WriteMetadata privledges will see the multiple Shared Data folders under the BIP Tree. The metadata identity that is denied ReadMetadata and WriteMetadata will only see the Shared Data folder that they built when they created a new SAS Library definition.
To correct this problem, the Metadata Administer should follow these steps:
- In the SAS Management Console, go to the Bi Manager plug–in.
- Right-click on the duplicate Shared Data folder and select Export. Follow the steps to export all of the objects.
- When the export completes, delete the duplicate Shared Data folder and all of its contents.
- Right-click on the original Shared Data folder and select Import. Follow the steps to import all of the objects in the package
To circumvent this problem, set the permissions on the libraries contained in the Shared Data folder. This will allow you to control what metadata identities have access to which library definitions.
Operating System and Release Information
SAS System | SAS Metadata Server | z/OS | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Windows Vista | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
HP-UX IPF | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux on Itanium | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Solaris for x64 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2009-04-16 11:10:05 |
Date Created: | 2009-03-31 16:10:22 |